Attaching patient context to a call history associated with voice communication

ABSTRACT

Systems, methods, and computer-readable media for declining, attaching, and editing patient context to mobile voice communication are provided. Patient demographic or alert information is attached to items within call histories associated with voice communication which are stored in the EMR and utilized for later analysis (e.g., analytics, patient progress, billing, reimbursement, staff scheduling, patient acuity, and the like). In embodiments, the context is declined, attached, or edited to items from the call history. In embodiments, the context is attached to items in the call history when the voice communication is initiated.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/710,409, titled “MULTI-ACTION BUTTON FOR MOBILE DEVICES AND ATTACHINGPATIENT CONTEXT TO A CALL HISTORY,” filed Oct. 5, 2012, which is herebyexpressly incorporated by reference in its entirety. This application isrelated by subject matter to U.S. application No. (not yet assigned)(Attorney Docket Number CRNI.175281), entitled “ATTACHING PATIENTCONTEXT TO A CALL HISTORY ASSOCIATED WITH VOICE COMMUNICATION”, which iscommonly assigned and filed on even date herewith, and is hereinincorporated by reference in its entirety.

BACKGROUND

Patient medical information, such as that contained in the EMR, allowshealth care providers to provide continuity of care to patients. Thus,it is critical for clinicians providing care to patients to review andcollaborate with other clinicians for each patient's medical record.However, these collaborations, while important to providing care forpatients, often goes undocumented because the ability to track mobilevoice communication as well as the content discussed is not currentlyavailable. This results in confusion and an inability to reference thedetails (e.g. patient name, relevant alerts, and the like) of a mobilevoice call and leaves the clinician and healthcare entity unable toappropriately track such information that may otherwise be useful inanalytics, tracking patient progress, billing, reimbursement, schedulingstaff, and patient acuity.

Further, when receiving alerts regarding a particular patient, it iscritical that these alerts are acknowledged in a timely manner. Often,it is necessary for an additional action to be taken in addition toacknowledging the alert. For example, the responding clinician may needto acknowledge (i.e., accept) the alert and call or text anotherclinician. Unfortunately, displays of current mobile devices arecluttered with option buttons which results in confusion and time lostpondering the correct action.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Embodiments of the present invention relate to declining, attaching, andediting patient context to mobile voice communication. Moreparticularly, patient demographic or alert information is attached to acall history which is stored in the electronic medical record (EMR) andutilized for later analysis (e.g., analytics, patient progress, billing,reimbursement, staff scheduling, patient acuity, and the like).

Accordingly, in one embodiment, computer storage media storingcomputer-executable instructions that, when executed by one or morecomputing devices, cause the one or more computing devices to perform amethod that facilitates attaching patient context to a call historyassociated with mobile voice communication is provided. A selection ofone of an alert from an alert list or one or more patients from apatient list is received. Context associated with the alert, the one ormore patients, or a combination thereof is provided. An indication thata first clinician is initiating a voice communication with a secondclinician is received. A selection of the second clinician from acontact list is received. The context is attached to a call historyassociated with the voice communication.

In another embodiment, a computer system to facilitate attaching patientcontext to a call history associated with mobile voice communication isprovided. The computer system comprises a processor coupled to acomputer storage medium, the computer storage medium having storedthereon a plurality of computer software components executable by theprocessor. A selection component receives a selection of one of an alertfrom an alert list or one or more patients from a patient list. Acontext component provides context associated with the alert, the one ormore patients, or a combination thereof. An indication componentreceives an indication that a first clinician is initiating a voicecommunication with a second clinician. A contact component receives aselection of the second clinician from a contact list. An attachmentcomponent attaches the context to a call history associated with thevoice communication.

In another embodiment, computer storage media having computer-executableinstructions embodied thereon that, when executed, produce a graphicaluser interface (GUI) to facilitate attaching patient context to a callhistory associated with mobile voice communication is provided. A listdisplay area displays one of an alert list or a patient list. A contextdisplay area displays context associated with an alert, one or morepatients, or a combination thereof. A call display area displays anindicator for initiating a voice communication. A contact display areadisplays a contact list. An attachment display area displays the contextattached to the call history associated with the voice communication.

BRIEF DESCRIPTION OF THE DRAWING

The present invention is described in detail below with reference to theattached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitablefor use in implementing the present invention;

FIG. 2 is a block diagram of an exemplary system for declining,attaching, or editing patient context to mobile voice communication, inaccordance with embodiments of the present invention;

FIGS. 3-19 are illustrative graphical user interface displays ofdeclining, attaching, or editing patient context to mobile voicecommunication, in accordance with embodiments of the present invention;

FIG. 20 is a flow diagram showing a method for attaching patient contextto mobile voice communication, in accordance with an embodiment of thepresent invention; and

FIG. 21 is a flow diagram showing a method for declining, attaching, orediting patient context to mobile voice communication, in accordancewith an embodiment of the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent components of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments of the present invention can positively impact healthorganizations' key imperatives in a variety of ways. Embodiments of thepresent invention provide context to voice communications that can beutilized in analytics, revealing trends, tracking resources, trackingpatient progress, billing, reimbursement, scheduling staff, and patientacuity. Embodiments of the present invention provide multi-actionbuttons on mobile devices that can be utilized by clinicians to improveresponse time and availability.

Referring now to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, for instance, amedical information computing system, on which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 100. It will be understood andappreciated by those of ordinary skill in the art that the illustratedmedical information computing system environment 100 is merely anexample of one suitable computing environment and is not intended tosuggest any limitation as to the scope of use or functionality of theinvention. Neither should the medical information computing systemenvironment 100 be interpreted as having any dependency or requirementrelating to any single component or combination of componentsillustrated therein.

Embodiments of the present invention may be operational with numerousother general purpose or special purpose computing system environmentsor configurations. Examples of well-known computing systems,environments, and/or configurations that may be suitable for use withthe present invention include, by way of example only, personalcomputers, server computers, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

Embodiments of the present invention may be described in the generalcontext of computer-executable instructions, such as program modules,being executed by a computer. Generally, program modules include, butare not limited to, routines, programs, objects, components, and datastructures that perform particular tasks or implement particularabstract data types. Embodiments of the present invention may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in local and/or remote computer storage mediaincluding, by way of example only, memory storage devices.

With continued reference to FIG. 1, the exemplary computing systemenvironment 100 includes a general purpose computing device in the formof a control server 102. Components of the control server 102 mayinclude, without limitation, a processing unit, internal system memory,and a suitable system bus for coupling various system components,including database cluster 104, with the control server 102. The systembus may be any of several types of bus structures, including a memorybus or memory controller, a peripheral bus, and a local bus, using anyof a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronic Standards Association (VESA) local bus, andPeripheral Component Interconnect (PCI) bus, also known as Mezzaninebus.

The control server 102 typically includes, or has access to, a varietyof computer readable media, for instance, database cluster 104. Computerreadable media can be any available media that may be accessed by server102, and includes volatile and nonvolatile media, as well as removableand non-removable media. By way of example, and not limitation, computerreadable media may include computer storage media and communicationmedia. Computer storage media may include, without limitation, volatileand nonvolatile media, as well as removable and nonremovable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, program modules, orother data. In this regard, computer storage media may include, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVDs) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage, orother magnetic storage device, or any other medium which can be used tostore the desired information and which may be accessed by the controlserver 102. Communication media typically embodies computer readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its attributes set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the abovealso may be included within the scope of computer readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 104, provide storage of computer readableinstructions, data structures, program modules, and other data for thecontrol server 102. The control server 102 may operate in a computernetwork 106 using logical connections to one or more remote computers108. Remote computers 108 may be located at a variety of locations in amedical or research environment, for example, but not limited to,clinical laboratories, hospitals and other inpatient settings,veterinary environments, ambulatory settings, medical billing andfinancial offices, hospital administration settings, home health careenvironments, and clinicians' offices. Clinicians may include, but arenot limited to, a treating physician or physicians, specialists such assurgeons, radiologists, cardiologists, and oncologists, emergencymedical technicians, physicians' assistants, nurse practitioners,nurses, nurses' aides, pharmacists, dieticians, microbiologists,laboratory experts, genetic counselors, researchers, veterinarians,students, and the like. The remote computers 108 may also be physicallylocated in non-traditional medical care environments so that the entirehealth care community may be capable of integration on the network. Theremote computers 108 may be personal computers, mobile devices, servers,routers, network PCs, peer devices, other common network nodes, or thelike, and may include some or all of the components described above inrelation to the control server 102. The devices can be personal digitalassistants or other like devices.

Exemplary computer networks 106 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the control server 102 may include a modem or other meansfor establishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the control server 102, in the database cluster 104, or on any of theremote computers 108. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 108. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., server 102 and remote computers 108) may beutilized.

In operation, a user may enter commands and information into the controlserver 102 or convey the commands and information to the control server102 via one or more of the remote computers 108 through input devices,such as a keyboard, a pointing device (commonly referred to as a mouse),a trackball, or a touch pad. Other input devices may include, withoutlimitation, microphones, satellite dishes, scanners, or the like.Commands and information may also be sent directly from a remotehealthcare device to the control server 102. In addition to a monitor,the control server 102 and/or remote computers 108 may include otherperipheral output devices, such as speakers and a printer.

Although many other internal components of the control server 102 andthe remote computers 108 are not shown, those of ordinary skill in theart will appreciate that such components and their interconnections arewell known. Accordingly, additional details concerning the internalconstruction of the control server 102 and the remote computers 108 arenot further disclosed herein.

With reference to FIG. 2, a block diagram is illustrated that shows anexemplary computing system architecture for implementing embodiments ofthe present invention. It will be appreciated that the computing systemarchitecture shown in FIG. 2 is merely an example of one suitablecomputing system and is not intended as having any dependency orrequirement related to any single module/component or combination ofmodules/components.

The computing system 200 includes one or more user devices 210 (e.g., amobile communication device), context engine 220, network 230, healthinformation system 240, and EMR 250. As utilized herein, the acronym“EMR” is not meant to be limiting, and may broadly refer to any or allaspects of the patient's medical record rendered in a digital format.Generally, the EMR is supported by systems configured to co-ordinate thestorage and retrieval of individual records with the aid of computingdevices. As such, a variety of types of healthcare-related informationmay be stored and accessed in this way. By way of example, the EMR maystore one or more of the following types of information: patientdemographic; medical history (e.g., examination and progress reports ofhealth and illnesses); medicine and allergy lists/immunization status;laboratory test results, radiology images (e.g., X-rays, CTs, MRIs,etc.); evidence-based recommendations for specific medical conditions; arecord of appointments and physician's notes; billing records; and datareceived from an associated medical device (e.g. alerts).

User device 210 receives and displays data from health informationsystem 240 and EMR 250 and communicates or otherwise makes the dataavailable to context engine 220. User device 210 also allows a clinicianto make voice communication calls, such as, for example, to otherclinicians. Although health information system 240 and EMR 250 areillustrated in FIG. 2 as separate components of computing system 200, itshould be appreciated that one or more of these components may beincluded in a single computing device.

Context engine 220 may reside on one or more computing devices, such as,for example, the control server 102 described above with reference toFIG. 1, user device 210, as shown in FIG. 2, or health informationsystem 240. By way of example, the control server 102 includes acomputer processor and may be a server, personal computer, desktopcomputer, laptop computer, handheld device, mobile device, consumerelectronic device, or the like. Context engine 220 comprises, in variousembodiments, selection component 221, context component 222, indicationcomponent 223, contact component 224, attachment component 225, itemselection component 226, and edit component 227.

In one embodiment, selection component 221 receives a selection of onean alert from an alert list or one or more patients from a patient list.As described above, the alert list and the patient list are communicatedfrom health information system 240 and/or EMR 250 via to the network tothe user device 210 where the data is communicated to or otherwiseshared with context engine 220. In various embodiments, the data isassociated with alerts and/or one or more patients. These alerts and/orone or more patients may be organized in an alert list and a patientlist, respectively. A first clinician may desire to discuss an alert orone or more patients with a second clinician. Accordingly, selectioncomponent 221 receives the selection made by the first clinician.

In one embodiment, context component 222 provides context associatedwith the alert, the one or more patients, or a combination thereof. Thecontext may include the alert or patient demographic information. Thecontext may further include additional information associated with thealert or patient demographic information, such as information receivedfrom health information system 240 or EMR 250. The additionalinformation may include protocols, encounter details, patientdemographics, care team information, family contacts, insuranceinformation, pharmacy information, and the like. The context providesthe clinician with information associated with the selected alert orpatient demographic information that can be attached to a call historyassociated with mobile voice communication for later use.

In one embodiment, indication component 223 receives an indication thatthe first clinician is initiating voice communication with a secondclinician. The indication may be made by pressing a button or activatingor triggering the phone (e.g., touch-activated screen, voice command,and the like) on the user device 210. Upon receiving the indication, thefirst clinician must select the recipient of the voice communication, orin this case, the second clinician. Contact component 224 receives aselection of the second clinician from a contact list. The contact listmay be a list displayed on the user device 210 or may be contactsmaintained by user device 210 or health information system 240. Or thecontact list may merely be a telephone number associated with the secondclinician that is selected by the first clinician. The selection may bemade by the first clinician selecting the second clinician from acontact list or call history displayed on the user device 210, by voicecommand, or by manually dialing the telephone number associated with thesecond clinician.

Once the contact is selected, in one embodiment, attachment component225 attaches the context to a call history associated with the voicecommunication. The call history may be available on the user device 210,or a device associated with the second clinician. Further, the callhistory may be communicated to medical information system 240 and/orstored in the EMR 250. For clarity, the call history may be an item inthe call history log of the user device that is associated with thevoice communication between the first clinician and the secondclinician.

In one embodiment, item selection component 226 receives a selection ofan item from a call history associated with voice communication. Forexample, an item within the call history on user device 210 may beassociated with a voice communication that did not have, or hadincomplete or incorrect context attached to it. The clinician may bereviewing items in the call history and determine that context should beadded, edited, or declined for a particular item. The clinician makesthe appropriate selection and item selection component 226 receives theselection accordingly.

In one embodiment, edit component 227 receives a selection to decline,attach, or edit context associated with the item. Edit component 227 maycause a pop-up to appear, allowing the clinician to select anappropriate action. After the clinician selects the item from the callhistory, the clinician selects the appropriate action. For example, theclinician may just want to indicate that no context is necessary andselects to decline context. Or the clinician may determine thatadditional or different detail is necessary and selects to edit context.Or the clinician may determine that no context was attached and the itemwould provide later benefits if context were attached. In this example,the clinician selects to attach context.

In one embodiment, context selection component 221, upon receiving theselection to attach or edit context, receives a selection of the contextto add or edit for the item. The context comprises an alert, one or morepatients, or a combination thereof. This allows the clinician to selectan alert, one or more patients (e.g., a first clinician discussesmultiple patients with a second clinician), or a combination thereof toattach or edit for the item in the call history. In one embodiment,attach component 225 attaches or edits the context associated with theitem in accordance with the selection of the context.

Referring now to FIG. 3, an illustrative screen display depicts listdisplay area 400 that displays a patient list, in accordance withembodiments of the present invention. List display area includes asearch bar 328 to search for a particular patient. List display areaalso includes unit organizers 310, 314 for organizing the patient listby unit. List display are also includes demographic bar 312, 316 thatdisplays context associated with a particular patient. Context includespatient name 336, date of birth 338, allergies 340, and location 342.List display area further includes tabs 330, 332, 334 for displayingparticular patients of a healthcare facility. For example, assigned tab430 includes in the patient list patients that are assigned to theclinician using the mobile device. Units tab 332 includes in the patientlist patients organized by unit (as depicted in FIG. 3). All tab 334includes all patients in the patient list. List display area 300 alsoincludes buttons 318, 320, 322, 324, 326 for displaying additionalitems. For example, patients button 318 displays a patient list in thelist display area 300. Staff button 320 displays a staff list in thelist display area 300. Alerts button 322 displays an alert list in thelist display area 300. Messages button 324 displays a message list inthe list display area 300. More button 326 displays other list topicsthat can be displayed in the list display area 300. As can beappreciated, other list topics can include any health care related topicthat may be useful to a clinician utilizing a mobile device in ahealthcare facility.

Referring now to FIG. 4, illustrative screen display depicts contextdisplay area 400, in accordance with embodiments of the presentinvention. Context display area 400 displays context associated with analert, one or more patients, or a combination thereof. Context displayarea 400 may be utilized to select the desired context to add to a callhistory associated with voice communication. For example, a firstclinician may desire to discuss a particular topic with a secondclinician regarding a patient. In order to record the topic ofdiscussion to the EMR, the first clinician selects the appropriate topicfrom context display area 400. Context display area 400 allows the firstclinician to review or select as detailed or general information asdesired. For example, context display area 400 includes patientinformation 412, encounter details 418, patient demographics 420, careteam 422, family contacts 424, insurance information 426, and preferredpharmacy 428. Call display area 414 displays an indicator for initiatinga voice communication. Once the desired information is reviewed and/orselected, the first clinician can select the indicator from call displayarea 414 or the text message button 416. The first clinician can returnto list display area 300 by selecting the patients button 410.

Referring now to FIG. 5, an illustrative screen display depicts acontact display area 510, in accordance with an embodiment of thepresent invention. As mentioned above, the first clinician may desire toview, select, or communicate (e.g., call or text message) a member ofthe care team for a particular patient. By selecting either the careteam 522, call display area 514, or text message button 516 causes acontact list to be displayed in the contact display area 510 on thefirst clinician's mobile device.

Referring now to FIG. 6, illustrative screen display depicts callhistory display area 600, in accordance with embodiments of the presentinvention. Call history display area 600 displays a call history ormessage history associated with a mobile device for a clinician.Attachment display area 612 displays the context attached to the callhistory 614 associated with the voice communication.

Referring now to FIG. 7, an illustrative screen display depicts listdisplay area 700 that displays an alert list, in accordance withembodiments of the present invention. List display area 700 includestabs for displaying alerts by category. For example, alerts can bedisplayed according to a timeframe, such as recent 710, or by severity.Or, all alerts related to a unit, a clinician, or a facility can bedisplayed.

Referring now to FIG. 8, an illustrative screen display depicts contextdisplay area 800, in accordance with embodiments of the presentinvention. Context display area 800 displays context associated with analert, one or more patients, or a combination thereof. Context displayarea includes patient information 810. Context display area 800 includesalert details 816, reminders 818, and communication history 820. Calldisplay area 812 displays an indicator for initiating a voicecommunication. Once the desired information is reviewed and/or selected,the first clinician can select the indicator from call display area 812or the group message button 814. The first clinician can return to listdisplay area 800 by selecting the patients button.

Referring now to FIG. 9, an illustrative screen display depicts acontact display area 900, in accordance with an embodiment of thepresent invention. As mentioned above, the first clinician may desire tocommunicate (e.g., call or text message) a member of the care team for aparticular patient. By selecting either the call display area 912 orgroup message button 914 causes a contact list to be displayed in thecontact display area 900 on the first clinician's mobile device. Contactdisplay area includes patient information 910, alert information 920,and a list of selectable or favorite contacts 930.

Referring now to FIG. 10, illustrative screen display depicts callhistory display area 1000, in accordance with embodiments of the presentinvention. Call history display area 1000 displays a call history ormessage history associated with a mobile device for a clinician.Attachment display area 1012 displays the context 1014 attached to thecall history 1016 associated with the voice communication.

Referring now to FIG. 11, an illustrative screen display depicts a callhistory display area 1100, in accordance with embodiments of the presentinvention. Call history display area 1100 includes history associatedwith voice communication and/or text message communication. Item displayarea 1112 further displays a patient button 1114 and an alert button1116 for a particular item 1118 in the call history. The clinician maydesire to select either the patient button 1114 or the alert button 1116to add the desired context to the particular item 1118.

Referring now to FIG. 12, an illustrative screen display depicts a listdisplay area 1200, in accordance with embodiments of the presentinvention. List display area includes tabs 1210, 1212, 1214 fordisplaying alerts by category. For example, alerts can be displayedaccording to a timeframe, such as most recent 1210, by severity 1212.Or, all 1214 alerts related to a unit, a clinician, or a facility can bedisplayed. Lists 1216, 1218 based on the category are displayed. Oncethe desired alert is selected, a done button 1220 allows the context tobe attached to the particular item in the call history.

Referring now to FIG. 13, an illustrative screen display depicts callhistory display area 1300, in accordance with embodiments of the presentinvention. Call history display area 1300 displays a call history ormessage history associated with communication with another clinician1310. Attachment display area 1312 displays the context 1314, 1316attached to the call history 1318 associated with the voicecommunication.

Referring now to FIG. 14, an illustrative screen display depicts a callhistory display area 1400, in accordance with embodiments of the presentinvention. Call history display area 1400 includes history associatedwith voice communication and/or text message communication. Item displayarea 1412 further displays a patient button 1414 and an alert button1416 for a particular item 1418 in the call history. The clinician maydesire to select either the patient button 1414 or the alert button 1416to add the desired context to the particular item 1418.

Referring now to FIG. 15, an illustrative screen display depicts a listdisplay area 1500, in accordance with embodiments of the presentinvention. List display area includes tabs 1510, 1512, 1514 fordisplaying patients category. For example, patients can be displayedaccording to assignment 1510, by unit 1512. Or, all 1514 patients for ahealthcare facility can be displayed. Lists 1516, 1518 based on thecategory are displayed. Once the desired patient is selected, a donebutton 1520 allows the context to be attached to the particular item inthe call history.

Referring now to FIG. 16, an illustrative screen display depicts callhistory display area 1600, in accordance with embodiments of the presentinvention. Call history display area 1600 displays a call history ormessage history associated with communication with another clinician1610. Attachment display area 1612 displays the context 1614, 1616attached to the call history 1618 associated with the voicecommunication.

Referring now to FIG. 17, an illustrative screen display depicts a callhistory display area 1700 and a selection display area 1712, inaccordance with embodiments of the present invention. Call historydisplay area 1700 displays a call history associated with voicecommunication. Selection display area 1712 displays an indicator forselecting to decline context to an item 1710 associated with the callhistory. Selecting to decline context to the item 1710 results in thedisplay merely displaying the length of the communication, rather thanincluding buttons for attaching context to the item.

Referring now to FIG. 18, an illustrative screen display depicts a callhistory display area 1800 and a selection display area 1812, inaccordance with embodiments of the present invention. Call historydisplay area 1800 displays a call history associated with voicecommunication. Selection display area 1812 displays an indicator forselecting to attach context to an item 1810 associated with the callhistory. Selecting to attach context to the item 1810 results allows theuser to attach context to the item, as described herein. Upon selectingto attach context to the item 1810 displays a context area that displayscontext comprising an alert, one or more patients, or a combinationthereof to associated with the item (as described herein).

Referring now to FIG. 19, an illustrative screen display depicts a callhistory display area 1900, a selection display area 1912, and attachmentdisplay area in accordance with embodiments of the present invention.Call history display area 1900 displays a call history associated withvoice communication. Selection display area displays an indicator forselecting to edit context to an item 1910 associated with the callhistory. Selecting to edit context to the item 1910 allows the user toedit context for the item. Upon selecting to edit context to the item1910 displays a context area that displays context comprising an alert,one or more patients, or a combination thereof to associated with theitem (as described herein for attaching context). Attachment displayarea displays the context associated with the item in accordance withthe selection of content.

Referring now to FIG. 20, an illustrative flow diagram 2000 is shown ofa method for attaching patient context to mobile voice communication, inaccordance with embodiments of the present invention. At step 2010, aselection of one of an alert from an alert list or one or more patientsfrom a patient list is received. Context associated with the alert, theone or more patients, or a combination thereof is provided at step 2020.At step 2030, an indication that a first clinician is initiating a voicecommunication with a second clinician is received. A selection of thesecond clinician is received, at step 2040, from a contact list. At step2050, the context is attached to a call history associated with thevoice communication. The call history and attached context is stored inthe EMR to be used for later purposes. In embodiments, a clinician isable to make a phone call while viewing patient details. When theclinician is viewing a patient's information, the patient's demographicbar is present on the display. This bar indicates that the informationthe user is viewing is related to the patient. The bar also indicatesthat patient context is attached to any action made when it is present.Thus, as the clinician makes a phone call or text message from a displaythat has a demographic bar (i.e., patient detail or alert detaildisplay), the patient context (alert and/or patient information) isincluded in the message log and stored in the EMR for future analytics.

Referring now to FIG. 21, an illustrative flow diagram 2100 is shown ofa method for declining, attaching, or editing patient context to mobilevoice communication, in accordance with embodiments of the presentinvention. At step 2110, a selection of an item from a call historyassociated with voice communication is received. A selection to decline,attach, or edit context associated with the item is received at step2120. A selection of the context to attach or edit is received at step2130. The context comprises an alert, one or more patients, or acombination thereof. At step 2140, the context to be associated with theitem is attached or edited in accordance with the selection of thecontext. When the clinician is not viewing a patient's information whilecommunicating with another clinician, a prompt is provided after thecommunication is complete. The prompt allows the user to attach patientsor alerts (i.e., context) to the communication. By attaching the contextto the communication, the clinician is able to include the patient oralert associated with the communication to the message history. Themessage history, including the context, is stored in the EMR for futureanalytics.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the scopeof the claims below. Embodiments of our technology have been describedwith the intent to be illustrative rather than restrictive. Alternativeembodiments will become apparent to readers of this disclosure after andbecause of reading it. Alternative means of implementing theaforementioned can be completed without departing from the scope of theclaims below. Certain features and subcombinations are of utility andmay be employed without reference to other features and subcombinationsand are contemplated within the scope of the claims.

Having thus described the invention, what is claimed is:
 1. One or morecomputer storage media storing computer-executable instructions that,when executed by one or more computing devices, cause the one or morecomputing devices to perform a method that facilitates attaching patientcontext to a call history associated with mobile voice communication:receiving a selection of one of an alert from an alert list or one ormore patients from a patient list; providing context associated with thealert, the one or more patients, or a combination thereof; receiving anindication that a first clinician is initiating a voice communicationwith a second clinician; receiving a selection of the second clinicianfrom a contact list; attaching the context to a call history associatedwith the voice communication.
 2. The media of claim 1, wherein the alertlist or patient list is communicated from a health information systemand/or electronic medical record (EMR).
 3. The media of claim 1, whereinthe context includes alert or patient demographic information.
 4. Themedia of claim 1, wherein the context includes one or more of protocols,encounter details, patient demographics, care team information, familycontacts, insurance information, pharmacy information.
 5. The media ofclaim 1, further comprising communicating the call history to medicalinformation system.
 6. The media of claim 1, further comprising storingthe call history in an electronic medical record (EMR).
 7. The media ofclaim 1, wherein the call history is an item in the call history log ofthe user device that is associated with the voice communication betweenthe first clinician and the second clinician.
 8. The media of claim 6,further comprising tracking patient progress.
 9. The media of claim 6,further comprising utilizing the call history for billing orreimbursement.
 10. The media of claim 6, further comprising utilizingthe call history for scheduling staff.
 11. A computer system tofacilitate attaching patient context to a call history associated withmobile voice communication, the computer system comprising a processorcoupled to a computer storage medium, the computer storage medium havingstored thereon a plurality of computer software components executable bythe processor, the computer software components comprising: a selectioncomponent for receiving a selection of one of an alert from an alertlist or one or more patients from a patient list; a context componentfor providing context associated with the alert, the one or morepatients, or a combination thereof; an indication component forreceiving an indication that a first clinician is initiating a voicecommunication with a second clinician; a contact component for receivinga selection of the second clinician from a contact list; an attachmentcomponent for attaching the context to a call history associated withthe voice communication.
 12. The system of claim 11, further comprisingan item selection component for receiving a selection of an item fromthe call history that the first clinician determines needs additionalcontext.
 13. The system of claim 12, further comprising a contextselection component for receiving additional context to add to the item.14. Computer storage media having computer-executable instructionsembodied thereon that, when executed, produce a graphical user interface(GUI) to facilitate attaching patient context to a call historyassociated with mobile voice communication, the GUI comprising: a listdisplay area that displays one of an alert list or a patient list; acontext display area that displays context associated with an alert, oneor more patients, or a combination thereof; a call display area thatdisplays an indicator for initiating a voice communication; a contactdisplay area that displays a contact list; and an attachment displayarea that displays the context attached to the call history associatedwith the voice communication.
 15. The media of claim 14, wherein thelist display area further displays a search bar to search for aparticular patient.
 16. The media of claim 14, wherein the list displayarea further displays unit organizers for organizing the patient list byunit.
 17. The media of claim 14, wherein the list display area furtherdisplays a demographic bar that displays context associated with aparticular patient.
 18. The media of claim 14, wherein the list displayarea further displays buttons for displaying additional items, theadditional items including a staff list, an alert list, a message list,and other topics.
 19. The media of claim 14, wherein the list displayarea further includes tabs for displaying particular patients of ahealthcare facility, the particular patients including all patientsassigned to the clinician, patients organized by unit, and all patientsin the patient list.
 20. The media of claim 14, wherein the contextincludes one or more of patient name, date of birth, allergies, andlocation.